DeepSeek’s Harness launch shifts focus from model pricing to the Agent runtime

DeepSeek’s recent rollout of Harness, released around the same time as the V4 Pro price increase, has prompted a new reading of the company’s strategy. The original MarsBit commentary argues that DeepSeek may be moving away from a playbook centered mainly on cheaper and stronger models, and toward control over where model calls actually happen. Harness is presented not as a polished end-user Agent product, but as a modular runtime framework. In the article’s description, models, tools, Skills, workflows, and UI are all separable parts, while plugins can be loaded, removed, and recombined on the fly. Underneath that sits Cordis, a kernel focused on plugin lifecycle management and system stability during change. The piece links that design to a broader idea: Agents that can adjust their operating environment while they run. Another point the article highlights is that Harness does not force users onto DeepSeek’s own models. Developers can define models, protocols, and Base URL settings, and can theoretically connect competing models. From that angle, the commentary suggests DeepSeek may be targeting the Agent runtime layer as infrastructure, closer to an operating system logic than a single-model product strategy. In that framing, V4 Pro’s higher pricing and Harness’s open design are part of the same shift toward ecosystem economics.